Agility ticket

Integration PR

Summary

This story introduces a new endpoint on the internal API to retrieve all moves for a service member. The moves are returned in a json object with structure {currentMove: [{}], previousMoves: [{}]}

Verification Steps for the Author

These are to be checked by the author.

• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

• Has the branch been pulled in and checked out?
• Have the BL acceptance criteria been met for this change?
• Was the CircleCI build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

• Instructions for starting storybook
• Instructions for starting the MilMove application
• Instructions for running tests

How to test

1. Create a service member and go through the process of requesting a move.
2. Approve the move as a counselor and approve the move as a TOO
3. Add shipments to the move as a prime user
4. Through Postman or swagger send a request to the /all_moves{serviceMemberId} endpoint of the internalAPI
5. You should get a response with an JSON object {currentMove: [{}], previousMoves: [{}]}. currentMove will have one move in it representing the move with the latest CreatedAt DateTime. PreviousMoves will have all other moves.
6. To test previous moves make sure the service member has more than one move

Backend

• Code follows the guidelines for Logging.
• The requirements listed in Querying the Database Safely have been satisfied.

Screenshots